home *** CD-ROM | disk | FTP | other *** search
- Date: Thu, 16 Jun 94 19:42:00 +0200
- Message-Id: <2e009d20@daggskim.ct.se>
- From: bo.leuf@daggskim.ct.se (Bo Leuf)
- Subject: Re: what about this?
- To: gem-list@world.std.com
- Precedence: bulk
-
-
- I got a bit more response from the "novel" idea than I expected, and interested
- that at least one saw this as potentially useful. I'm not saying that it
- _should_ be used, but considering some of the more arcane doubleclick&drag
- shift-ctrl stuff that can pop up in discussions like this, my initial reaction
- to my own idea was... well, just maybe...
-
- Anyway, to meet the "nonsensical" counter:
-
- > [...] What if a person accidentally types a word with TWO
- > letters in it which are exactly the same, and it's not meant as a
- > double-
- > key click? Say, for instance, "Stopping", "Cancelling", "Accidents",
- > etc. You get the idea. It doesn't make sense.
-
- This kind of keyboard "doubleclick" would only have to be a reasonable command
- when we have a Ctrl-key combination. It boils down to being part of the normal
- test-if-Ctrl part of the application's keyboard event loop. If Ctrl is not
- held, then the code does not have to pause to consider if this is a single or
- double version.
-
- I agree with the comment that the interpretation is better reversed, i.e. that
- a single Ctrl-F (say) means call-up-the-dialog, and the double Ctrl-F-F would
- be the skip-the-dialog-and-get-on-with-it response. The handling of this should
- be possible within the application code with simple timing and testing and not
- require any event_multi() changes. I doubt that there would be any significant
- problems with repeat; again remember that the test need only consider
- Ctrl-something, not any and every key typed.
-
- I'm going to try this concept out in some code sometime soon and get the feel
- of it. Thanks for your replies. Presumably this thread can end here.
-
- (illegible signature) Bo Leuf
-
-
-
-
-